SQL Server Requirements
Refer to Supported Spatial Databases
SQL Server stores spatial data using one of two data types.
|
Name |
Data type |
SRID |
|---|---|---|
|
Geography |
Latitude/longitude |
Required. Typically 4326 for WGS84, 4269 for NAD83 |
|
Geometry |
Cartesian coordinates |
Optional but strongly recommended. |
To review the spatial reference systems (SRIDs) supported by SQL Server:
SELECT * FROM SYS.spatial_reference_systems
To review SRIDs by text:
SELECT * FROM sys.spatial_reference_systems WHERE well_known_text LIKE '%ED50%'
SQL Server Database User Permissions
When OpenCities Map encounters Primary Keys where an identity column is specified, it performs some management of the Primary Key values using setidentity_insert <tablename> on. To do this, the database needs the Alter permission either granted on the table or the database. If this permission is not set the system will respond with a cannot find object because it does not exist or you do not have permissions error. Set the alter permission on the desired tables prior to working with those features in OpenCities Map.
Other Primary Key data types that OpenCities Map supports do not require the alter permission, and OpenCities Map is able to generate new Primary Keys having just the db_datareader and db_datawriter roles. Posting data will work with numerous other numeric or character Primary Key data-types. Those tested include: integer, big int, decimal, float, varchar, char, uniqueidentifier, and sequence generated Primary Keys.